tripit.com

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

Registration

info

.com generic · InterNetX GmbH · expires 2027-03-11

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
InterNetX GmbH
Registered
11 March 1999
Last changed
9 November 2023
Expires
11 March 2027
Status
client transfer prohibited
Registry nameservers
a1-111.akam.net, a10-66.akam.net, a13-67.akam.net, a18-64.akam.net, a28-65.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-03-11 #3
    The registration is valid until 2027-03-11 (139 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

a1-111.akam.net, a10-66.akam.net, a13-67.akam.net, a18-64.akam.net, a28-65.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
a1-111.akam.net, a10-66.akam.net, a13-67.akam.net, a18-64.akam.net, a28-65.akam.net
NS in the zone
a1-111.akam.net, a10-66.akam.net, a13-67.akam.net, a18-64.akam.net, a28-65.akam.net, a5-66.akam.net
NameserverAddressesNetwork (AS)Glue
a1-111.akam.net193.108.91.111 2600:1401:2::6fAS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a10-66.akam.net96.7.50.66 2600:1480:d000::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a13-67.akam.net2.22.230.67 2600:1480:800::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a18-64.akam.net95.101.36.64 2600:1480:4800::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a28-65.akam.net95.100.173.65 2600:1480:d800::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a5-66.akam.net (zone only)95.100.168.66 2600:1480:b000::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 5 nameservers #6
    Delegated to a1-111.akam.net, a10-66.akam.net, a13-67.akam.net, a18-64.akam.net, a28-65.akam.net.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: a5-66.akam.net. a1-111.akam.net, a10-66.akam.net, a13-67.akam.net, a18-64.akam.net, a28-65.akam.net, a5-66.akam.net report NS a1-111.akam.net a10-66.akam.net a13-67.akam.net a18-64.akam.net a28-65.akam.net a5-66.akam.net.
    #7
  • ✓ 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.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 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 .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-111.akam.net 193.108.91.111NOERROR, 3 ms, authoritativenoyes / yesrefused41824.4
a1-111.akam.net 2600:1401:2::6fNOERROR, 3 ms, authoritativenoyes / yesrefused41824.7
a10-66.akam.net 96.7.50.66NOERROR, 3 ms, authoritativenoyes / yesrefused48878.30
a10-66.akam.net 2600:1480:d000::42NOERROR, 4 ms, authoritativenoyes / yesrefused48878.29
a13-67.akam.net 2.22.230.67NOERROR, 4 ms, authoritativenoyes / yesrefused41824.5
a13-67.akam.net 2600:1480:800::43NOERROR, 4 ms, authoritativenoyes / yesrefused41824.10
a18-64.akam.net 95.101.36.64NOERROR, 3 ms, authoritativenoyes / yesrefused48878.26
a18-64.akam.net 2600:1480:4800::40NOERROR, 4 ms, authoritativenoyes / yesrefused48878.30
a28-65.akam.net 95.100.173.65NOERROR, 3 ms, authoritativenoyes / yesrefused48878.27
a28-65.akam.net 2600:1480:d800::41NOERROR, 4 ms, authoritativenoyes / yesrefused48878.33
a5-66.akam.net 95.100.168.66NOERROR, 3 ms, authoritativenoyes / yesrefused41824.9
a5-66.akam.net 2600:1480:b000::42NOERROR, 4 ms, authoritativenoyes / yesrefused41824.9

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-111.akam.net: "41824.4"; a1-111.akam.net: "41824.7"; a10-66.akam.net: "48878.30"; a10-66.akam.net: "48878.29"; a13-67.akam.net: "41824.5"; a13-67.akam.net: "41824.10"; a18-64.akam.net: "48878.26"; a18-64.akam.net: "48878.30"; a28-65.akam.net: "48878.27"; a28-65.akam.net: "48878.33"; a5-66.akam.net: "41824.9". 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

info

serial 2019300526 · primary ns0.concur.net

Found

Primary (MNAME)
ns0.concur.net
Contact (RNAME)
eoperator.concur.com
Serial
2019300526
Refresh / retry
10800 s / 3600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
a1-111.akam.net (193.108.91.111)2019300526
a1-111.akam.net (2600:1401:2::6f)2019300526
a10-66.akam.net (96.7.50.66)2019300526
a10-66.akam.net (2600:1480:d000::42)2019300526
a13-67.akam.net (2.22.230.67)2019300526
a13-67.akam.net (2600:1480:800::43)2019300526
a18-64.akam.net (95.101.36.64)2019300526
a18-64.akam.net (2600:1480:4800::40)2019300526
a28-65.akam.net (95.100.173.65)2019300526
a28-65.akam.net (2600:1480:d800::41)2019300526
a5-66.akam.net (95.100.168.66)2019300526
a5-66.akam.net (2600:1480:b000::42)2019300526

Checks

  • ✓ Serial 2019300526 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 14d, negative TTL 1h.
  • i
    Hidden master (not resolvable)
    The primary nameserver ns0.concur.net is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact eoperator@concur.com #25
    The SOA RNAME eoperator.concur.com means eoperator@concur.com.
  • ✓ Timestamp serial #26
    The serial 2019300526 is a Unix timestamp (2033-12-27 12:48 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

16 records at the apex

Found

Read from
193.108.91.111:53
TypeValueTTL
SOAns0.concur.net. eoperator.concur.com. 2019300526 10800 3600 1209600 3600300
NSa13-67.akam.net.300
NSa28-65.akam.net.300
NSa18-64.akam.net.300
NSa1-111.akam.net.300
NSa10-66.akam.net.300
NSa5-66.akam.net.300
A104.82.98.6320
AAAA2a02:26f0:b700:880::11a020
AAAA2a02:26f0:b700:893::11a020
MX10 mx.tripit.com.300
TXT"v=spf1 ip4:52.89.110.61 ip4:52.24.108.48 ip4:34.223.218.184 ip4:129.33.239.160 ip4:129.33.239.164 mx include:amazonses.com include:aspmx.googlemail.com include:email.freshdesk.com ~all"300
TXT"google-site-verification=gOeMZ0uWZi0ZmspK8X9xtFeTrS2HvTUIetRf8jZKJa0"300
TXT"google-site-verification=9SodKrgLLjMfIiLediO0LV4A9fKEpvM7N3u06kJFixI"300
TXT"7ywmqmfvgybzpfzwfgfdw4bf8fhfnj8l"300
TXT"fpc5zj2x8w0npph31dt1n6my82v3ng6x"300

Checks

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