wordpress.com

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

Registration

info

.com generic · MarkMonitor Inc. · expires 2033-03-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
3 March 2000
Last changed
28 August 2023
Expires
3 March 2033
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, ns4.wordpress.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 2033-03-03 #3
    The registration is valid until 2033-03-03 (2324 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

info

ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, ns4.wordpress.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, ns4.wordpress.com
NS in the zone
ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, ns4.wordpress.com
NameserverAddressesNetwork (AS)Glue
ns1.wordpress.com198.181.116.9 2a04:fa87:ffff::c6b5:7409AS2635 AUTOMATTIC - Automattic, Inc, US AS2635 AUTOMATTIC - Automattic, Inc, US198.181.116.9 2a04:fa87:ffff::c6b5:7409
ns2.wordpress.com198.181.117.9 2a04:fa87:ffff::c6b5:7509AS2635 AUTOMATTIC - Automattic, Inc, US AS2635 AUTOMATTIC - Automattic, Inc, US198.181.117.9 2a04:fa87:ffff::c6b5:7509
ns3.wordpress.com192.0.74.9 2620:115:c00f::c000:4a09AS2635 AUTOMATTIC - Automattic, Inc, US AS2635 AUTOMATTIC - Automattic, Inc, US192.0.74.9 2620:115:c00f::c000:4a09
ns4.wordpress.com192.0.75.9 2620:115:c00f::c000:4b09AS2635 AUTOMATTIC - Automattic, Inc, US AS2635 AUTOMATTIC - Automattic, Inc, US192.0.75.9 2620:115:c00f::c000:4b09

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, ns4.wordpress.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, ns4.wordpress.com.
  • ✓ 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 4 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS2635 (AUTOMATTIC - Automattic, Inc, US): 8 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

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.wordpress.com 198.181.116.9NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns1.wordpress.com 2a04:fa87:ffff::c6b5:7409NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.wordpress.com 198.181.117.9NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.wordpress.com 2a04:fa87:ffff::c6b5:7509NOERROR, 4 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns3.wordpress.com 192.0.74.9NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns3.wordpress.com 2620:115:c00f::c000:4a09NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns4.wordpress.com 192.0.75.9NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns4.wordpress.com 2620:115:c00f::c000:4b09NOERROR, 3 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

Checks

  • ✓ All respond #14
    All 8 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: ns1.wordpress.com: "Served by PowerDNS - https://www.powerdns.com/"; ns2.wordpress.com: "Served by PowerDNS - https://www.powerdns.com/"; ns3.wordpress.com: "Served by PowerDNS - https://www.powerdns.com/"; ns4.wordpress.com: "Served by PowerDNS - https://www.powerdns.com/".
    #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

warn

serial 2005071886 · primary ns1.wordpress.com

Found

Primary (MNAME)
ns1.wordpress.com
Contact (RNAME)
mmmmmm.gmail.com
Serial
2005071886
Refresh / retry
14400 s / 7200 s
Expire
604800 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1.wordpress.com (198.181.116.9)2005071886
ns1.wordpress.com (2a04:fa87:ffff::c6b5:7409)2005071886
ns2.wordpress.com (198.181.117.9)2005071886
ns2.wordpress.com (2a04:fa87:ffff::c6b5:7509)2005071886
ns3.wordpress.com (192.0.74.9)2005071886
ns3.wordpress.com (2620:115:c00f::c000:4a09)2005071886
ns4.wordpress.com (192.0.75.9)2005071886
ns4.wordpress.com (2620:115:c00f::c000:4b09)2005071886

Checks

  • ✓ Serial 2005071886 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 4h, retry 2h, expire 7d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.wordpress.com is one of the listed nameservers.
  • ✓ Contact mmmmmm@gmail.com #25
    The SOA RNAME mmmmmm.gmail.com means mmmmmm@gmail.com.
  • ✓ Date-based serial #26
    The serial 2005071886 follows the YYYYMMDDnn convention (2005-07-18).

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

16 records at the apex

Found

Read from
198.181.116.9:53
TypeValueTTL
SOAns1.wordpress.com. mmmmmm.gmail.com. 2005071886 14400 7200 604800 6014400
NSns2.wordpress.com.14400
NSns3.wordpress.com.14400
NSns1.wordpress.com.14400
NSns4.wordpress.com.14400
A192.0.78.9300
A192.0.78.17300
MX10 mx-ams.automattic.com.3600
MX10 mx-dfw.automattic.com.3600
TXT"google-site-verification=CW2JYOoHSXW8x6QyQO_a0edu0gNOKsLIHcO49QquLdU"3600
TXT"yahoo-verification-key=GqtxTvPQ+tFgwrCg9xNl6srlPSpDkTIj6q9YzADxxdE="3600
TXT"v=spf1 include:_spf.automattic.com include:servers.mcsv.net include:_spf-wwd.automattic.com include:mail.zendesk.com include:sendgrid.net include:145630858.spf04.hubspotemail.net include:amazonses.com -all"3600
TXT"openai-domain-verification=dv-AKnzAsfVXHG2wucO1Bcx2JC7"3600
CAA0 issuewild "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489"300
CAA0 issue "letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/36334489"300
CAA0 iodef "mailto:caa@automattic.com"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1h, NS 4h. The NS TTL at the parent is 2d and in the zone 4h; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.