neworleans.com

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

Registration

info

.com generic · Network Solutions, LLC · expires 2031-12-21

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Network Solutions, LLC
Registered
22 December 1994
Last changed
22 October 2026
Expires
21 December 2031
Status
client transfer prohibited
Registry nameservers
ns79.worldnic.com, ns80.worldnic.com
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 2031-12-21 #3
    The registration is valid until 2031-12-21 (1885 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns79.worldnic.com, ns80.worldnic.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns79.worldnic.com, ns80.worldnic.com
NS in the zone
ns79.worldnic.com, ns80.worldnic.com
NameserverAddressesNetwork (AS)Glue
ns79.worldnic.com162.159.26.27AS13335 CLOUDFLARENET - Cloudflare, Inc., US162.159.26.27
ns80.worldnic.com162.159.27.78AS13335 CLOUDFLARENET - Cloudflare, Inc., US162.159.27.78

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns79.worldnic.com, ns80.worldnic.com.
    #6
  • ✓ 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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 2 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 .com
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

1 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns79.worldnic.com 162.159.26.27NOERROR, 28 ms, authoritativenono / yesrefused2026.10.8
ns80.worldnic.com 162.159.27.78REFUSED, 17 ms, NOT authoritativenono / yesrefused2026.10.8

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns80.worldnic.com (162.159.27.78): REFUSED, authoritative=false.
    #15
  • ✓ 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: ns79.worldnic.com: "2026.10.8"; ns80.worldnic.com: "2026.10.8". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns79.worldnic.com (162.159.26.27): ; ns80.worldnic.com (162.159.27.78): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 126091411 · primary ns79.worldnic.com

Found

Primary (MNAME)
ns79.worldnic.com
Contact (RNAME)
namehost.worldnic.com
Serial
126091411
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Checks

  • ✓ Serial 126091411 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns79.worldnic.com is one of the listed nameservers.
  • ✓ Contact namehost@worldnic.com #25
    The SOA RNAME namehost.worldnic.com means namehost@worldnic.com.
  • ✓ Counter serial #26
    The serial 126091411 is a plain counter.

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

13 records at the apex

Found

Read from
162.159.26.27:53
TypeValueTTL
SOANS79.WORLDNIC.com. namehost.WORLDNIC.com. 126091411 10800 3600 604800 36007200
NSns80.worldnic.com.7200
NSns79.worldnic.com.7200
A34.74.254.273600
MX10 neworleans-com.mail.protection.outlook.com.3600
TXT"google-site-verification=P9kRly9jBx3CVFJ4ucuYNY7m8L0rYbmX7geHuXLlGHc"7200
TXT"apple-domain-verification=Z21PnDPlXfvNNXOf"1800
TXT"facebook-domain-verification=cc4tahhc8qyw52c31ncnab36jwblyl"3600
TXT"MS=ms13778315"3600
TXT"google-site-verification=CZMaOsE-T50RZKZxGQXIHa-KlyU81n0hdy1GKby9UqU"7200
TXT"v=spf1 include:spf.protection.outlook.com ip4:162.88.37.102 ip4:162.88.37.103 ip4:67.225.242.81 ip4:173.213.225.60 include:spf-us.emailsignatures365.com include:_spf.act-on.net include:shops.shopify.com include:servers.mcsv.net ~all"3600
TXT"uloch16k8sreh8k10hdpa77eks"7200
TXT"facebook-domain-verification=e3rjiysqxjvxnaaz6n8kmc576geu6r"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, 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