serialssolutions.com

Checked 22 October 2026, 10:40 UTC · via 8.8.8.8
✗Problems found
22 passed 2 warnings 1 failed 6 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2027-01-29

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
29 January 2000
Last changed
28 December 2025
Expires
29 January 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-01-29 #3
    The registration is valid until 2027-01-29 (98 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

fail

dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net
NS in the zone
dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns0-mnm-ol8.dc04
NameserverAddressesNetwork (AS)Glue
dns1.p04.nsone.net198.51.44.4 2620:4d:4000:6259:7:4:0:1AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns2.p04.nsone.net198.51.45.4 2a00:edc0:6259:7:4::2AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns3.p04.nsone.net198.51.44.68 2620:4d:4000:6259:7:4:0:3AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
dns4.p04.nsone.net198.51.45.68 2a00:edc0:6259:7:4::4AS62597 NSONE - NSONE Inc, US AS62597 NSONE - NSONE Inc, US-
ns0-mnm-ol8.dc04 (zone only)(does not resolve)-

Checks

  • ✓ 4 nameservers #6
    Delegated to dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns0-mnm-ol8.dc04. dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net report NS dns1.p04.nsone.net dns2.p04.nsone.net dns3.p04.nsone.net dns4.p04.nsone.net ns0-mnm-ol8.dc04.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✗
    Nameserver names don't resolve
    These nameservers have no A or AAAA record, so they can't be reached (lame delegation): ns0-mnm-ol8.dc04.
    #9
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS62597 (NSONE - NSONE Inc, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.p04.nsone.net 198.51.44.4NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns1.p04.nsone.net 2620:4d:4000:6259:7:4:0:1NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns2.p04.nsone.net 198.51.45.4NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns2.p04.nsone.net 2a00:edc0:6259:7:4::2NOERROR, 3 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns3.p04.nsone.net 198.51.44.68NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns3.p04.nsone.net 2620:4d:4000:6259:7:4:0:3NOERROR, 6 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns4.p04.nsone.net 198.51.45.68NOERROR, 4 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9
dns4.p04.nsone.net 2a00:edc0:6259:7:4::4NOERROR, 3 ms, authoritativenoyes / yesrefused19dd46e347df36b70933bf2be8023258586586a9

Checks

  • ✓ All respond #14
    All 8 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns1.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns2.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns3.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9"; dns4.p04.nsone.net: "19dd46e347df36b70933bf2be8023258586586a9".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2024111110 · primary ns0-mnm-ol8.dc04

Found

Primary (MNAME)
ns0-mnm-ol8.dc04
Contact (RNAME)
hostmaster.serialssolutions.com
Serial
2024111110
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
7200 s

Serial per nameserver

NameserverSerial
dns1.p04.nsone.net (198.51.44.4)2024111110
dns1.p04.nsone.net (2620:4d:4000:6259:7:4:0:1)2024111110
dns2.p04.nsone.net (198.51.45.4)2024111110
dns2.p04.nsone.net (2a00:edc0:6259:7:4::2)2024111110
dns3.p04.nsone.net (198.51.44.68)2024111110
dns3.p04.nsone.net (2620:4d:4000:6259:7:4:0:3)2024111110
dns4.p04.nsone.net (198.51.45.68)2024111110
dns4.p04.nsone.net (2a00:edc0:6259:7:4::4)2024111110

Checks

  • ✓ Serial 2024111110 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 2h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0-mnm-ol8.dc04 is one of the listed nameservers.
  • ✓ Contact hostmaster@serialssolutions.com #25
    The SOA RNAME hostmaster.serialssolutions.com means hostmaster@serialssolutions.com.
  • ✓ Date-based serial #26
    The serial 2024111110 follows the YYYYMMDDnn convention (2024-11-11).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

17 records at the apex

Found

Read from
198.51.44.4:53
TypeValueTTL
SOAns0-mnm-ol8.dc04. hostmaster.serialssolutions.com. 2024111110 28800 7200 604800 720086400
NSns0-mnm-ol8.dc04.7200
NSdns2.p04.nsone.net.7200
NSdns4.p04.nsone.net.7200
NSdns1.p04.nsone.net.7200
NSdns3.p04.nsone.net.7200
A216.147.212.23014400
MX10 serialssolutions-com.mail.protection.outlook.com.300
TXT"_1saadomgkjmf8a65ypeowxpzuflgoxp"300
TXT"v=spf1 mx include:spf-na.exlibrisgroup.com include:spf.protection.outlook.com ~all"300
TXT"MS=ms43576165"300
TXT"v=verifydomain MS=ms78621907"300
TXT"0c47e61fcb8f4898ae6b5f4e6f1ea927"300
TXT"5484dc6d04cd46fd91088c06370b1bdb"300
TXT"g64mc8ws2l1nbcnvpt1529zfd2czbpwm"300
TXT"sz2hdh237ypmwbx9rd2d7mdm77b65zhj"300
TXT"lnLUUjn/Wo63oFMaQYNWOUAKqhN8Gk58NLEN8M54teT8FTEoHshXkyEZhQ3I6iTxuTQ0eIIe9WqAoeuURd/0rA=="300

Checks

  • ✓ TTLs within range #32
    TTLs: A 4h, MX 5m, NS 2h. The NS TTL at the parent is 2d and in the zone 2h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35