Hostname
okaydate.com
Last fetched
okaydate.com resolves to 7 IPv4 addresses operated by AKAMAI-LINODE-AP Akamai Connected Cloud in US. WHOIS lists iana:2288 as the registrar.
Nutrition Label
Resolution chain
okaydate.com resolves to 7 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 172.233.219.123 | 172.233.208.0/20 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
| 172.233.219.49 | 172.233.208.0/20 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
| 172.233.219.78 | 172.233.208.0/20 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
| 172.237.146.25 | 172.237.128.0/19 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
| 172.237.146.38 | 172.237.128.0/19 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
| 172.237.146.8 | 172.237.128.0/19 | AS63949 | AKAMAI-LINODE-AP Akamai Connected Cloud | US |
| 85.131.245.124 | 85.131.192.0/18 | AS131965 | XSERVER Xserver Inc. | JP |
WHOIS identity
- Registrar
- iana:2288
- Organization
- perfect privacy,
- Contact emails
Subdomains
2 observed subdomains of okaydate.com.
| Subdomain |
|---|
| mail.okaydate.com |
| www.okaydate.com |
Web-graph footprint
Distinct hostnames that link to or from okaydate.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
3 SPF mechanisms authorising senders for okaydate.com.
| Mechanism | Target |
|---|---|
| SPF_A | okaydate.com |
| SPF_IP | 85.131.245.124 |
| SPF_MX | okaydate.com |
Related pages
Pivot deeper into the graph from okaydate.com.
- IP · 172.233.219.123
- ASN · AS63949AKAMAI-LINODE-AP Akamai Connected Cloud
- Registrar · iana:2288
- Country · US
- Email · 2vd1g45e2ch61betpibvt4h7a6@domaindiscreet.com
- TLD · .com
- Browse hostnames · ok…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "okaydate.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.