travelclick.com

Checked 22 October 2026, 11:12 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 4 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2028-04-20

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
21 April 1998
Last changed
5 August 2026
Expires
20 April 2028
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
a1-186.akam.net, a12-67.akam.net, a13-64.akam.net, a18-65.akam.net, a2-66.akam.net, a9-67.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 2028-04-20 #3
    The registration is valid until 2028-04-20 (545 days).
  • ✓ Transfer locked #4
    Registry status: client delete 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

a1-186.akam.net, a12-67.akam.net, a13-64.akam.net, a18-65.akam.net, a2-66.akam.net, a9-67.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
a1-186.akam.net, a12-67.akam.net, a13-64.akam.net, a18-65.akam.net, a2-66.akam.net, a9-67.akam.net
NS in the zone
a1-186.akam.net, a12-67.akam.net, a13-64.akam.net, a18-65.akam.net, a2-66.akam.net, a9-67.akam.net
NameserverAddressesNetwork (AS)Glue
a1-186.akam.net193.108.91.186 2600:1401:2::baAS20940 AKAMAI-ASN1 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a12-67.akam.net184.26.160.67 2600:1480:f000::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a13-64.akam.net2.22.230.64 2600:1480:800::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a18-65.akam.net95.101.36.65 2600:1480:4800::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a2-66.akam.net95.100.174.66 2600:1480:7000::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a9-67.akam.net184.85.248.67 2a02:26f0:117::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-186.akam.net, a12-67.akam.net, a13-64.akam.net, a18-65.akam.net, a2-66.akam.net, a9-67.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 6 IPv4 /24s and 6 IPv6 /48s.
  • ✓ 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): 11 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-186.akam.net 193.108.91.186NOERROR, 5 ms, authoritativenoyes / yesrefused41824.4
a1-186.akam.net 2600:1401:2::baNOERROR, 5 ms, authoritativenoyes / yesrefused41824.9
a12-67.akam.net 184.26.160.67NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
a12-67.akam.net 2600:1480:f000::43NOERROR, 5 ms, authoritativenoyes / yesrefused48878.32
a13-64.akam.net 2.22.230.64NOERROR, 7 ms, authoritativenoyes / yesrefused41824.4
a13-64.akam.net 2600:1480:800::40NOERROR, 6 ms, authoritativenoyes / yesrefused41824.9
a18-65.akam.net 95.101.36.65NOERROR, 5 ms, authoritativenoyes / yesrefused48878.33
a18-65.akam.net 2600:1480:4800::41NOERROR, 5 ms, authoritativenoyes / yesrefused48878.32
a2-66.akam.net 95.100.174.66NOERROR, 4 ms, authoritativenoyes / yesrefused48878.30
a2-66.akam.net 2600:1480:7000::42NOERROR, 5 ms, authoritativenoyes / yesrefused48878.32
a9-67.akam.net 184.85.248.67NOERROR, 6 ms, authoritativenoyes / yesrefused41824.5
a9-67.akam.net 2a02:26f0:117::43NOERROR, 5 ms, authoritativenoyes / yesrefused41824.10

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: a1-186.akam.net: "41824.4"; a1-186.akam.net: "41824.9"; a12-67.akam.net: "48878.32"; a13-64.akam.net: "41824.4"; a13-64.akam.net: "41824.9"; a18-65.akam.net: "48878.33"; a18-65.akam.net: "48878.32"; a2-66.akam.net: "48878.30"; a2-66.akam.net: "48878.32"; a9-67.akam.net: "41824.5"; a9-67.akam.net: "41824.10". 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 2018082976 · primary a2-66.akam.net

Found

Primary (MNAME)
a2-66.akam.net
Contact (RNAME)
hostmaster.travelclick.com
Serial
2018082976
Refresh / retry
10800 s / 600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
a1-186.akam.net (193.108.91.186)2018082976
a1-186.akam.net (2600:1401:2::ba)2018082976
a12-67.akam.net (184.26.160.67)2018082976
a12-67.akam.net (2600:1480:f000::43)2018082976
a13-64.akam.net (2.22.230.64)2018082976
a13-64.akam.net (2600:1480:800::40)2018082976
a18-65.akam.net (95.101.36.65)2018082976
a18-65.akam.net (2600:1480:4800::41)2018082976
a2-66.akam.net (95.100.174.66)2018082976
a2-66.akam.net (2600:1480:7000::42)2018082976
a9-67.akam.net (184.85.248.67)2018082976
a9-67.akam.net (2a02:26f0:117::43)2018082976

Checks

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

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

18 records at the apex

Found

Read from
193.108.91.186:53
TypeValueTTL
SOAa2-66.akam.net. hostmaster.travelclick.com. 2018082976 10800 600 604800 36003600
NSa18-65.akam.net.7200
NSa13-64.akam.net.7200
NSa2-66.akam.net.7200
NSa12-67.akam.net.7200
NSa1-186.akam.net.7200
NSa9-67.akam.net.7200
A199.167.218.1083600
MX10 travelclick-com.mail.protection.outlook.com.3600
TXT"oVqbqtOl8/w/QFO7+ts+zyddVH4zpwhjDNsuR/nzZrTF1HkN757g3dSN0YrUg0j/Ssk6nbx5rd06Wo8cUNVBOg=="300
TXT"v=spf1 ip4:199.167.217.90 ip4:199.167.223.12 ip4:209.242.69.231 ip4:199.167.217.33 include:spf.zml0.com include:spf.protection.outlook.com include:_spf.salesforce.com include:_spf.travelclick.com ~all"300
TXT"A0M0A22889"300
TXT"facebook-domain-verification=3tplfx4i434ep1as8csrgqzmhz65e2"300
TXT"MS=ms71928501"300
TXT"webexdomainverification.4C675B8A9F83B136E053AB06FC0A3F65=389c37a7-aca9-4f56-9ff4-47a842d2f578"300
TXT"google-site-verification=BStfIyg9WiqQEF1pDp1-uBocFzExTvcHXP7ST1dtUwk"300
TXT"_dia0l18mkpnnqhi0yrqc7oppuqgq3d0"300
TXT"_lxq0lolt5qkk52bxemv7qu74d68gixy"300

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