upgradedpoints.com

Checked 22 October 2026, 11:15 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 5 info

Registration

info

.com generic · NameCheap, Inc. · expires 2031-01-25

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
NameCheap, Inc.
Registered
25 January 2015
Last changed
11 September 2024
Expires
25 January 2031
Status
client transfer prohibited
Registry nameservers
jule.ns.cloudflare.com, rajeev.ns.cloudflare.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-01-25 #3
    The registration is valid until 2031-01-25 (1556 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

info

jule.ns.cloudflare.com, rajeev.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
jule.ns.cloudflare.com, rajeev.ns.cloudflare.com
NS in the zone
jule.ns.cloudflare.com, rajeev.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
jule.ns.cloudflare.com172.64.32.175 173.245.58.175 108.162.192.175 2606:4700:50::adf5:3aaf 2a06:98c1:50::ac40:20af 2803:f800:50::6ca2:c0afAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.192.175 172.64.32.175 173.245.58.175 2606:4700:50::adf5:3aaf 2803:f800:50::6ca2:c0af 2a06:98c1:50::ac40:20af
rajeev.ns.cloudflare.com108.162.193.224 172.64.33.224 173.245.59.224 2803:f800:50::6ca2:c1e0 2606:4700:58::adf5:3be0 2a06:98c1:50::ac40:21e0AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.193.224 172.64.33.224 173.245.59.224 2606:4700:58::adf5:3be0 2803:f800:50::6ca2:c1e0 2a06:98c1:50::ac40:21e0

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: jule.ns.cloudflare.com, rajeev.ns.cloudflare.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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
jule.ns.cloudflare.com 172.64.32.175NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jule.ns.cloudflare.com 173.245.58.175NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jule.ns.cloudflare.com 108.162.192.175NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jule.ns.cloudflare.com 2606:4700:50::adf5:3aafNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jule.ns.cloudflare.com 2a06:98c1:50::ac40:20afNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jule.ns.cloudflare.com 2803:f800:50::6ca2:c0afNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
rajeev.ns.cloudflare.com 108.162.193.224NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
rajeev.ns.cloudflare.com 172.64.33.224NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
rajeev.ns.cloudflare.com 173.245.59.224NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
rajeev.ns.cloudflare.com 2803:f800:50::6ca2:c1e0NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
rajeev.ns.cloudflare.com 2606:4700:58::adf5:3be0NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
rajeev.ns.cloudflare.com 2a06:98c1:50::ac40:21e0NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: jule.ns.cloudflare.com: "2026.10.2"; rajeev.ns.cloudflare.com: "2026.10.2". 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

pass

serial 2417359006 · primary jule.ns.cloudflare.com

Found

Primary (MNAME)
jule.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2417359006
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
jule.ns.cloudflare.com (172.64.32.175)2417359006
jule.ns.cloudflare.com (173.245.58.175)2417359006
jule.ns.cloudflare.com (108.162.192.175)2417359006
jule.ns.cloudflare.com (2606:4700:50::adf5:3aaf)2417359006
jule.ns.cloudflare.com (2a06:98c1:50::ac40:20af)2417359006
jule.ns.cloudflare.com (2803:f800:50::6ca2:c0af)2417359006
rajeev.ns.cloudflare.com (108.162.193.224)2417359006
rajeev.ns.cloudflare.com (172.64.33.224)2417359006
rajeev.ns.cloudflare.com (173.245.59.224)2417359006
rajeev.ns.cloudflare.com (2803:f800:50::6ca2:c1e0)2417359006
rajeev.ns.cloudflare.com (2606:4700:58::adf5:3be0)2417359006
rajeev.ns.cloudflare.com (2a06:98c1:50::ac40:21e0)2417359006

Checks

  • ✓ Serial 2417359006 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver jule.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2417359006 is a Unix timestamp (2046-08-08 16:36 UTC).

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

14 records at the apex

Found

Read from
172.64.32.175:53
TypeValueTTL
SOAjule.ns.cloudflare.com. dns.cloudflare.com. 2417359006 10000 2400 604800 18001800
NSjule.ns.cloudflare.com.86400
NSrajeev.ns.cloudflare.com.86400
A151.101.193.9160
A151.101.129.9160
A151.101.65.9160
A151.101.1.9160
MX1 smtp.google.com.300
TXT"Sendinblue-code:b7327b512026f355106abe2dee2537d9"300
TXT"facebook-domain-verification=ei9ayjk56p63vtu00vamr1typpad23"300
TXT"google-site-verification=JORyBck_cwu1WOtXxjgQnUMC7kW8iDZIeSt7ahGsekk"300
TXT"google-site-verification=KZnlXhgNpTc4C-rFO_9upZbsRFQWFXT8mRDbhkD4AFc"300
TXT"google-site-verification=blPe2PnjuDnjlBPoEoHKp4ql1EkrF4i_XkQSjkmBR0g"300
TXT"v=spf1 include:_spf.google.com ~all"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; 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