Hostname
thisromance.com
Last fetched
thisromance.com resolves to 104.26.14.180, announced in 104.28.10.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. thisromance.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.26.14.180
104.28.10.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.15.180
104.28.10.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.69.174
172.68.15.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:269
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- domains@hugedomains.com, nmpdvnph@whoisprivacyprotect.com, support@dropcatch.com, 85bf960f27aa7e2f9e1436d6c79a0134c2844114a5ce63f8621bc2021f6f360a@thisromance.com.whoisproxy.org, 9ca0d48fae1117f8f704a3032543c9367b5a26d595a9d66038df7926a2ae8b0a@thisromance.com.whoisproxy.org, 9f3a204fe8f9a01b68a61d0ca6eee22a89a97d6020c768413cda41f106c1894a@thisromance.com.whoisproxy.org, acb78d68a3a76d459aca117d9fc92ba22e7d336d81310d06391682d4a1506431@thisromance.com.whoisproxy.org
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- carl.ns.cloudflare.com
- tess.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: mail.zendesk.com
- include: spf.sendios.io
Threat-feed evidence
History
Related pages
Pivot from thisromance.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "thisromance.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.