site.com

Checked 22 October 2026, 10:43 UTC · via 8.8.8.8
!Passed with warnings
28 passed 2 warnings 0 failed 5 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2028-01-02

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
30 December 1994
Last changed
1 December 2025
Expires
2 January 2028
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
dns01.salesforce.com, dns02.salesforce.com, dns03.salesforce.com, dns04.salesforce.com, dns05.salesforce.com, dns06.salesforce.com, u2dns1.salesforce.com, u2dns2.salesforce.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 2028-01-02 #3
    The registration is valid until 2028-01-02 (436 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

warn

dns01.salesforce.com, dns02.salesforce.com, dns03.salesforce.com, dns04.salesforce.com, dns05.salesforce.com, dns06.salesforce.com, u2dns1.salesforce.com, u2dns2.salesforce.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns01.salesforce.com, dns02.salesforce.com, dns03.salesforce.com, dns04.salesforce.com, dns05.salesforce.com, dns06.salesforce.com, u2dns1.salesforce.com, u2dns2.salesforce.com
NS in the zone
dns01.salesforce.com, dns02.salesforce.com, dns03.salesforce.com, dns04.salesforce.com, dns05.salesforce.com, dns06.salesforce.com, u2dns1.salesforce.com, u2dns2.salesforce.com
NameserverAddressesNetwork (AS)Glue
dns01.salesforce.com204.74.108.235 2001:502:f3ff::9AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US204.74.108.235
dns02.salesforce.com204.74.109.235 2610:a1:1014::9AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US204.74.109.235
dns03.salesforce.com199.7.68.235 2610:a1:1015::9AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US199.7.68.235
dns04.salesforce.com199.7.69.235 2001:502:4612::9AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US199.7.69.235
dns05.salesforce.com204.74.114.235 2610:a1:1016::9AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US204.74.114.235
dns06.salesforce.com204.74.115.235 2610:a1:1017::9AS12008 VERCARA - Vercara, LLC, US AS12008 VERCARA - Vercara, LLC, US204.74.115.235
u2dns1.salesforce.com156.154.151.1 2610:a1:31d2::53AS399153 SECURITYSERVICES - Vercara, LLC, US AS399155 SECURITYSERVICES - Vercara, LLC, US156.154.151.1 2610:a1:31d2::53
u2dns2.salesforce.com204.74.121.1 2610:a1:32d2::53AS399154 SECURITYSERVICES - Vercara, LLC, US AS399154 SECURITYSERVICES - Vercara, LLC, US204.74.121.1 2610:a1:32d2::53

Checks

  • ✓ 8 nameservers #6
    Delegated to dns01.salesforce.com, dns02.salesforce.com, dns03.salesforce.com, dns04.salesforce.com, dns05.salesforce.com, dns06.salesforce.com, u2dns1.salesforce.com, u2dns2.salesforce.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: dns01.salesforce.com (glue 204.74.108.235, zone 204.74.108.235, 2001:502:f3ff::9); dns02.salesforce.com (glue 204.74.109.235, zone 204.74.109.235, 2610:a1:1014::9); dns03.salesforce.com (glue 199.7.68.235, zone 199.7.68.235, 2610:a1:1015::9); dns04.salesforce.com (glue 199.7.69.235, zone 199.7.69.235, 2001:502:4612::9); dns05.salesforce.com (glue 204.74.114.235, zone 204.74.114.235, 2610:a1:1016::9); dns06.salesforce.com (glue 204.74.115.235, zone 204.74.115.235, 2610:a1:1017::9). Update the glue at your registrar.
    #8
  • ✓ 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 8 IPv4 /24s and 8 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS12008 (VERCARA - Vercara, LLC, US): 12 addresses; AS399153 (SECURITYSERVICES - Vercara, LLC, US): 1 address; AS399154 (SECURITYSERVICES - Vercara, LLC, US): 2 addresses; AS399155 (SECURITYSERVICES - Vercara, LLC, US): 1 address.
  • 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

info

16 of 16 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns01.salesforce.com 204.74.108.235NOERROR, 3 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns01.salesforce.com 2001:502:f3ff::9NOERROR, 4 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns02.salesforce.com 204.74.109.235NOERROR, 3 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns02.salesforce.com 2610:a1:1014::9NOERROR, 4 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns03.salesforce.com 199.7.68.235NOERROR, 3 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns03.salesforce.com 2610:a1:1015::9NOERROR, 4 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns04.salesforce.com 199.7.69.235NOERROR, 31 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns04.salesforce.com 2001:502:4612::9NOERROR, 32 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns05.salesforce.com 204.74.114.235NOERROR, 3 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns05.salesforce.com 2610:a1:1016::9NOERROR, 3 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns06.salesforce.com 204.74.115.235NOERROR, 31 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
dns06.salesforce.com 2610:a1:1017::9NOERROR, 32 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
u2dns1.salesforce.com 156.154.151.1NOERROR, 4 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
u2dns1.salesforce.com 2610:a1:31d2::53NOERROR, 4 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
u2dns2.salesforce.com 204.74.121.1NOERROR, 10 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver
u2dns2.salesforce.com 2610:a1:32d2::53NOERROR, 10 ms, authoritativenoyes / yesrefusedUltraDNS Nameserver

Checks

  • ✓ All respond #14
    All 16 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: dns01.salesforce.com: "UltraDNS Nameserver"; dns02.salesforce.com: "UltraDNS Nameserver"; dns03.salesforce.com: "UltraDNS Nameserver"; dns04.salesforce.com: "UltraDNS Nameserver"; dns05.salesforce.com: "UltraDNS Nameserver"; dns06.salesforce.com: "UltraDNS Nameserver"; u2dns1.salesforce.com: "UltraDNS Nameserver"; u2dns2.salesforce.com: "UltraDNS Nameserver".
    #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 2012032180 · primary dns01.salesforce.com

Found

Primary (MNAME)
dns01.salesforce.com
Contact (RNAME)
hostmaster.salesforce.com
Serial
2012032180
Refresh / retry
1800 s / 900 s
Expire
2592000 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
dns01.salesforce.com (204.74.108.235)2012032180
dns01.salesforce.com (2001:502:f3ff::9)2012032180
dns02.salesforce.com (204.74.109.235)2012032180
dns02.salesforce.com (2610:a1:1014::9)2012032180
dns03.salesforce.com (199.7.68.235)2012032180
dns03.salesforce.com (2610:a1:1015::9)2012032180
dns04.salesforce.com (199.7.69.235)2012032180
dns04.salesforce.com (2001:502:4612::9)2012032180
dns05.salesforce.com (204.74.114.235)2012032180
dns05.salesforce.com (2610:a1:1016::9)2012032180
dns06.salesforce.com (204.74.115.235)2012032180
dns06.salesforce.com (2610:a1:1017::9)2012032180
u2dns1.salesforce.com (156.154.151.1)2012032180
u2dns1.salesforce.com (2610:a1:31d2::53)2012032180
u2dns2.salesforce.com (204.74.121.1)2012032180
u2dns2.salesforce.com (2610:a1:32d2::53)2012032180

Checks

  • ✓ Serial 2012032180 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 30m, retry 15m, expire 30d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns01.salesforce.com is one of the listed nameservers.
  • ✓ Contact hostmaster@salesforce.com #25
    The SOA RNAME hostmaster.salesforce.com means hostmaster@salesforce.com.
  • ✓ Date-based serial #26
    The serial 2012032180 follows the YYYYMMDDnn convention (2012-03-21).

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
1 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
28529ECDSAP256SHA256 (13)SHA256 C94305ECC490580C…yes

DNSKEY in the zone

Key tagRoleAlgorithm
26119ZSK (256)ECDSAP256SHA256 (13)
28529KSK (257)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 28529 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-01 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-01 22:38 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

warn

15 records at the apex

Found

Read from
204.74.108.235:53
TypeValueTTL
SOAdns01.salesforce.com. hostmaster.salesforce.com. 2012032180 1800 900 2592000 18003600
NSdns01.salesforce.com.7200
NSdns02.salesforce.com.7200
NSdns03.salesforce.com.7200
NSdns04.salesforce.com.7200
NSdns05.salesforce.com.7200
NSdns06.salesforce.com.7200
NSu2dns1.salesforce.com.7200
NSu2dns2.salesforce.com.7200
A35.176.92.19120
A34.226.36.51120
A34.211.108.46120
A13.113.196.52120
TXT"v=spf1 -all"3600
TXT"00do0000000bfdpeaq"3600

Checks

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