r7.com

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

Registration

info

.com generic · GoDaddy.com, LLC · expires 2027-04-15

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
14 April 1996
Last changed
13 March 2025
Expires
15 April 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
asia1.akam.net, eur5.akam.net, ns1-228.akam.net, ns1-95.akam.net, usc3.akam.net, use5.akam.net, use9.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-04-15 #3
    The registration is valid until 2027-04-15 (174 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew 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

info

asia1.akam.net, eur5.akam.net, ns1-228.akam.net, ns1-95.akam.net, usc3.akam.net, use5.akam.net, use9.akam.net, usw1.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
asia1.akam.net, eur5.akam.net, ns1-228.akam.net, ns1-95.akam.net, usc3.akam.net, use5.akam.net, use9.akam.net, usw1.akam.net
NS in the zone
asia1.akam.net, eur5.akam.net, ns1-228.akam.net, ns1-95.akam.net, usc3.akam.net, use5.akam.net, use9.akam.net, usw1.akam.net
NameserverAddressesNetwork (AS)Glue
asia1.akam.net95.100.175.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
eur5.akam.net23.74.25.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-228.akam.net193.108.91.228 2600:1401:2::e4AS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
ns1-95.akam.net193.108.91.95 2600:1401:2::5fAS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usc3.akam.net96.7.50.64AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use5.akam.net2.16.40.64 2600:1403:a::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
use9.akam.net72.246.46.65AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
usw1.akam.net23.61.199.66AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 8 nameservers #6
    Delegated to asia1.akam.net, eur5.akam.net, ns1-228.akam.net, ns1-95.akam.net, usc3.akam.net, use5.akam.net, use9.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 7 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS20940 (AKAMAI-ASN1 - Akamai International B.V., NL): 2 addresses; 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: asia1.akam.net, eur5.akam.net, usc3.akam.net, use9.akam.net, usw1.akam.net.
    #13

Nameservers

warn

11 of 11 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
asia1.akam.net 95.100.175.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.31
eur5.akam.net 23.74.25.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.33
ns1-228.akam.net 193.108.91.228NOERROR, 3 ms, authoritativenoyes / yesrefused41824.11
ns1-228.akam.net 2600:1401:2::e4NOERROR, 4 ms, authoritativenoyes / yesrefused41824.6
ns1-95.akam.net 193.108.91.95NOERROR, 3 ms, authoritativenoyes / yesrefused41824.9
ns1-95.akam.net 2600:1401:2::5fNOERROR, 4 ms, authoritativenoyes / yesrefused41824.8
usc3.akam.net 96.7.50.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.31
use5.akam.net 2.16.40.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.29
use5.akam.net 2600:1403:a::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.27
use9.akam.net 72.246.46.65NOERROR, 4 ms, authoritativenoyes / yesrefused48878.32
usw1.akam.net 23.61.199.66NOERROR, 3 ms, authoritativenoyes / yesrefused41824.5

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: asia1.akam.net: "48878.31"; eur5.akam.net: "48878.33"; ns1-228.akam.net: "41824.11"; ns1-228.akam.net: "41824.6"; ns1-95.akam.net: "41824.9"; ns1-95.akam.net: "41824.8"; usc3.akam.net: "48878.31"; use5.akam.net: "48878.29"; use5.akam.net: "48878.27"; use9.akam.net: "48878.32"; usw1.akam.net: "41824.5". 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 2022102084 · primary asia1.akam.net

Found

Primary (MNAME)
asia1.akam.net
Contact (RNAME)
hostmaster.r7.com
Serial
2022102084
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
asia1.akam.net (95.100.175.64)2022102084
eur5.akam.net (23.74.25.64)2022102084
ns1-228.akam.net (193.108.91.228)2022102084
ns1-228.akam.net (2600:1401:2::e4)2022102084
ns1-95.akam.net (193.108.91.95)2022102084
ns1-95.akam.net (2600:1401:2::5f)2022102084
usc3.akam.net (96.7.50.64)2022102084
use5.akam.net (2.16.40.64)2022102084
use5.akam.net (2600:1403:a::40)2022102084
use9.akam.net (72.246.46.65)2022102084
usw1.akam.net (23.61.199.66)2022102084

Checks

  • ✓ Serial 2022102084 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver asia1.akam.net is one of the listed nameservers.
  • ✓ Contact hostmaster@r7.com #25
    The SOA RNAME hostmaster.r7.com means hostmaster@r7.com.
  • ✓ Date-based serial #26
    The serial 2022102084 follows the YYYYMMDDnn convention (2022-10-20).

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

20 records at the apex

Found

Read from
95.100.175.64:53
TypeValueTTL
SOAasia1.akam.net. hostmaster.r7.com. 2022102084 3600 600 604800 30086400
NSusw1.akam.net.86400
NSusc3.akam.net.86400
NSuse9.akam.net.86400
NSns1-228.akam.net.86400
NSasia1.akam.net.86400
NSuse5.akam.net.86400
NSeur5.akam.net.86400
NSns1-95.akam.net.86400
A3.33.133.1960
A13.248.211.23360
MX10 mx2.r7.email.locaweb.com.br.60
MX10 inbound-smtp.us-east-1.amazonaws.com.60
MX20 mx3.r7.email.locaweb.com.br.60
MX20 mx4.r7.email.locaweb.com.br.60
MX5 mx1.r7.email.locaweb.com.br.60
TXT"v=spf1 include:amazonses.com include:_spf.r7.com include:_lw.r7.com ?all"1800
TXT"lfjgprjmpl5clscnsb0k1y3hyn334kqx"1800
TXT"google-site-verification=P8RYEKfn5NVEnBYV6IOSfN-7ss0b80-AMVk6ss-Pgrg"1800
TXT"_qnxd7pikj0yjps14dizumwyrtb92s1i"1800

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (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