Hostname
writing.com
Last fetched
writing.com resolves to 2 IPv4 addresses operated by VKT-HK Viking Telecom Limited in US. WHOIS lists iana:1659 as the registrar.
Nutrition Label
Resolution chain
writing.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 198.74.52.13 | 198.74.52.0/22 | AS63949 | VKT-HK Viking Telecom Limited | US |
| 50.116.34.225 | 50.116.32.0/20 | AS63949 | VKT-HK Viking Telecom Limited | US |
WHOIS identity
- Registrar
- iana:1659
- Organization
- domain privacy service fbo registrant.
- Contact emails
Subdomains
101 observed subdomains of writing.com.
Showing 25 of 101. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from writing.com in the public web crawl.
1,020 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
16 SPF mechanisms authorising senders for writing.com.
| Mechanism | Target |
|---|---|
| SPF_A | writing.com |
| SPF_IP | 172.105.135.91 |
| SPF_IP | 192.155.94.75 |
| SPF_IP | 198.74.52.13 |
| SPF_IP | 23.92.29.131 |
| SPF_IP | 2600:3c02:0:0:f03c:92ff:fe46:55d4 |
| SPF_IP | 2600:3c02:0:0:f03c:92ff:fe6d:21bc |
| SPF_IP | 2600:3c02:0:0:f03c:92ff:fed3:1dd6 |
| SPF_IP | 2600:3c02:0:0:f03c:93ff:feb4:8cc5 |
| SPF_IP | 2600:3c02:0:0:f03c:95ff:fe5b:9b0d |
| SPF_IP | 2600:3c02:0:0:f03c:95ff:feb5:c673 |
| SPF_IP | 2600:3c02:0:0:f03c:95ff:fee3:67be |
| SPF_IP | 45.33.99.110 |
| SPF_IP | 45.56.117.107 |
| SPF_IP | 50.116.34.225 |
| SPF_MX | writing.com |
Related pages
Pivot deeper into the graph from writing.com.
- IP · 198.74.52.13
- ASN · AS63949VKT-HK Viking Telecom Limited
- Registrar · iana:1659
- Country · US
- Email · 3772060@privacy-link.com
- TLD · .com
- Browse hostnames · wr…
- 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: "writing.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.