SurfaceMap › i › ispsystem.com

ispsystem.com

Checked 2026-10-22 09:22 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

fail

21 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC !Records

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.ispsystem.net (62.109.13.129): dial tcp 62.109.13.129:53: connect: connection refused; ns2.ispsystem.net (94.130.173.174): dial tcp 94.130.173.174:53: connect: connection refused.
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.ispsystem.net, ns2.ispsystem.net. ns-1403.awsdns-47.org, ns-1960.awsdns-53.co.uk, ns-245.awsdns-30.com, ns-865.awsdns-44.net report NS ns-1403.awsdns-47.org ns-1960.awsdns-53.co.uk ns-245.awsdns-30.com ns-865.awsdns-44.net. ns1.ispsystem.net, ns2.ispsystem.net report NS ns1.ispsystem.net ns2.ispsystem.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.ispsystem.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 5 2026 13:33:43 by root@localhost)"; ns2.ispsystem.net: "PowerDNS Authoritative Server 4.9.17 (built Aug 5 2026 13:33:43 by root@localhost)". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1 on ns-1403.awsdns-47.org (205.251.197.123), ns-1403.awsdns-47.org (2600:9000:5305:7b00::1), ns-1960.awsdns-53.co.uk (205.251.199.168), ns-1960.awsdns-53.co.uk (2600:9000:5307:a800::1), ns-245.awsdns-30.com (205.251.192.245), ns-245.awsdns-30.com (2600:9000:5300:f500::1), ns-865.awsdns-44.net (205.251.195.97), ns-865.awsdns-44.net (2600:9000:5303:6100::1); 2026092502 on ns1.ispsystem.net (62.109.13.129), ns2.ispsystem.net (94.130.173.174). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change.
    #32

Recent checks

✗

Full report

Domain & DNS report for ispsystem.com ›

Mail

warn

26 passed 3 warn 0 failed

Areas

✓SPF !DMARC ✓DKIM !DNSSEC ✓MX !TLS iBIMI

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for ispsystem.com ›