nbcsandiego.com

Checked 22 October 2026, 10:01 UTC · via 8.8.8.8
!Passed with warnings
21 passed 4 warnings 0 failed 6 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2027-07-27

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
27 July 1999
Last changed
25 June 2025
Expires
27 July 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, use3.akam.net, usw1.akam.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-07-27 #3
    The registration is valid until 2027-07-27 (278 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, use3.akam.net, usw1.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, use3.akam.net, usw1.akam.net
NS in the zone
asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, use3.akam.net, usw1.akam.net
NameserverAddressesNetwork (AS)Glue
asia2.akam.net95.101.36.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
asia3.akam.net23.211.61.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
aus1.akam.net184.85.248.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur3.akam.net95.100.174.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur4.akam.net84.53.139.64--
ns1-102.akam.net193.108.91.102 2600:1401:2::66AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-161.akam.net193.108.91.161 2600:1401:2::a1AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use3.akam.net96.7.49.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usw1.akam.net23.61.199.66AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 9 nameservers #6
    Delegated to asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, ns1-102.akam.net, ns1-161.akam.net, use3.akam.net, usw1.akam.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2600:1401:2::/48, while the other address family is spread over several networks.
    #10
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 1 address; AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 9 addresses.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: asia2.akam.net, asia3.akam.net, aus1.akam.net, eur3.akam.net, eur4.akam.net, use3.akam.net, usw1.akam.net.
    #13

Nameservers

warn

11 of 11 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
asia2.akam.net 95.101.36.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
asia3.akam.net 23.211.61.64NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
aus1.akam.net 184.85.248.65NOERROR, 3 ms, authoritativenoyes / yesrefused41824.9
eur3.akam.net 95.100.174.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
eur4.akam.net 84.53.139.64NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
ns1-102.akam.net 193.108.91.102NOERROR, 3 ms, authoritativenoyes / yesrefused41824.4
ns1-102.akam.net 2600:1401:2::66NOERROR, 3 ms, authoritativenoyes / yesrefused41824.11
ns1-161.akam.net 193.108.91.161NOERROR, 3 ms, authoritativenoyes / yesrefused41824.6
ns1-161.akam.net 2600:1401:2::a1NOERROR, 4 ms, authoritativenoyes / yesrefused41824.11
use3.akam.net 96.7.49.65NOERROR, 3 ms, authoritativenoyes / yesrefused41824.4
usw1.akam.net 23.61.199.66NOERROR, 4 ms, authoritativenoyes / yesrefused41824.6

Checks

  • ✓ All respond #14
    All 11 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: asia2.akam.net: "48878.32"; asia3.akam.net: "48878.29"; aus1.akam.net: "41824.9"; eur3.akam.net: "48878.32"; eur4.akam.net: "41824.11"; ns1-102.akam.net: "41824.4"; ns1-102.akam.net: "41824.11"; ns1-161.akam.net: "41824.6"; ns1-161.akam.net: "41824.11"; use3.akam.net: "41824.4"; usw1.akam.net: "41824.6". Hide or replace the version string.
    #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

warn

serial 2014091874 · primary ns1.nbcuni.com

Found

Primary (MNAME)
ns1.nbcuni.com
Contact (RNAME)
domain\.admin.nbcuni.com
Serial
2014091874
Refresh / retry
900 s / 3600 s
Expire
2592000 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
asia2.akam.net (95.101.36.64)2014091874
asia3.akam.net (23.211.61.64)2014091874
aus1.akam.net (184.85.248.65)2014091874
eur3.akam.net (95.100.174.64)2014091874
eur4.akam.net (84.53.139.64)2014091874
ns1-102.akam.net (193.108.91.102)2014091874
ns1-102.akam.net (2600:1401:2::66)2014091874
ns1-161.akam.net (193.108.91.161)2014091874
ns1-161.akam.net (2600:1401:2::a1)2014091874
use3.akam.net (96.7.49.65)2014091874
usw1.akam.net (23.61.199.66)2014091874

Checks

  • ✓ Serial 2014091874 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 15m is outside 20m–1d; retry 1h should be shorter than refresh 15m. Current values: refresh 15m, retry 1h, expire 30d, negative TTL 15m.
    #23
  • i
    Hidden master
    The primary nameserver ns1.nbcuni.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact domain.admin@nbcuni.com #25
    The SOA RNAME domain\.admin.nbcuni.com means domain.admin@nbcuni.com.
  • ✓ Date-based serial #26
    The serial 2014091874 follows the YYYYMMDDnn convention (2014-09-18).

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

warn

18 records at the apex

Found

Read from
95.101.36.64:53
TypeValueTTL
SOAns1.nbcuni.com. domain\.admin.nbcuni.com. 2014091874 900 3600 2592000 90043200
NSusw1.akam.net.99
NSaus1.akam.net.99
NSasia2.akam.net.99
NSns1-102.akam.net.99
NSuse3.akam.net.99
NSns1-161.akam.net.99
NSeur4.akam.net.99
NSasia3.akam.net.99
NSeur3.akam.net.99
A104.101.238.2320
MX20 mx0a-00176a04.pphosted.com.99
MX20 mx0b-00176a04.pphosted.com.99
MX10 mxa-00176a04.gslb.pphosted.com.99
MX10 mxb-00176a04.gslb.pphosted.com.99
TXT"v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all"99
TXT"_rjxdmmrk8ydtpvnkou9g5tsfz7su3xa"99
TXT"MS=ms34782219"99

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), MX (1m39s), NS (1m39s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1m39s; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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