wordcamp.org: IP address, DNS records and WHOIS
Live lookup data for wordcamp.org: the IP addresses it resolves to, the DNS records it publishes, and its registration details. The data below is fetched when this page is built and refreshed daily.
At a glance
DNS records
A
| 66.6.42.106 | TTL 300 |
AAAA
No public records of this type are currently published.
CNAME
No public records of this type are currently published.
MX
| aspmx.l.google.com | 1 |
| alt1.aspmx.l.google.com | 5 |
| alt2.aspmx.l.google.com | 5 |
| alt3.aspmx.l.google.com | 10 |
| alt4.aspmx.l.google.com | 10 |
NS
| ns1.wordpress.org |
| ns2.wordpress.org |
| ns3.wordpress.org |
| ns4.wordpress.org |
TXT
| v=spf1 ip4:66.6.42.0/24 include:helpscoutemail.com include:_spf.google.com ~all |
| google-site-verification=IHZ7S4aIYKic_NyW8FKjhbOZuNKctz7KE4VuJo3ofU8 |
| google-site-verification=Kz1UsndVXnxBfn5xiELGVHDqobB0ggCjsJxRYp-oLhw |
SOA
- Primary nameserver
- ns1.wordpress.org
- Hostmaster
- hostmaster@wordpress.org
- Serial
- 2017012001
- Refresh
- 1200 s (20 minutes)
- Retry
- 7200 s (2 hours)
- Expire
- 3600000 s (1000 hours)
- Minimum TTL
- 86400 s (1 day)
CAA
| 0 issue "letsencrypt.org" |
WHOIS registration data
- Registrar
- MarkMonitor Inc.
- Registered
- Jul 8, 2006
- Expires
- Jul 8, 2028
- Last changed
- Aug 12, 2026
- Status
- client delete prohibited, client transfer prohibited, client update prohibited
- Nameservers
- ns1.wordpress.org, ns2.wordpress.org, ns3.wordpress.org, ns4.wordpress.org
- DNSSEC signed
- No
FAQ
wordcamp.org currently resolves to 66.6.42.106. Large sites often publish several addresses and rotate them, so the list can differ between checks and between locations.
wordcamp.org is registered through MarkMonitor Inc.. The registrant's identity is not published in the public registration record — most owners use a privacy service or the data is redacted.
wordcamp.org is served by ns1.wordpress.org, ns2.wordpress.org, ns3.wordpress.org, ns4.wordpress.org. These are the authoritative nameservers that publish its DNS records.
Run a fresh check
Records change. Run the live tools for an up-to-the-minute answer: