Hostname
otpco.com
Last fetched
otpco.com resolves to 104.18.16.122, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. otpco.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.18.16.122
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.17.122
104.18.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- perfect privacy,
- Contact emails
- ac27f6ch3pq@networksolutionsprivateregistration.com, ay7y35zs3s9@networksolutionsprivateregistration.com, dm5e25kg2d7@networksolutionsprivateregistration.com, ef98c8dp6d2@networksolutionsprivateregistration.com, gy4239z937z@networksolutionsprivateregistration.com, jv8xf2468ep@networksolutionsprivateregistration.com, kt2cy5sv8s8@networksolutionsprivateregistration.com, m46mx5y556n@networksolutionsprivateregistration.com, qr5ah2fj9pz@networksolutionsprivateregistration.com, rb5499sb7rt@networksolutionsprivateregistration.com, sv6vw6sd4vx@networksolutionsprivateregistration.com, ts8659258ja@networksolutionsprivateregistration.com, ug88q8tg7nx@networksolutionsprivateregistration.com, wp8zw5fx42w@networksolutionsprivateregistration.com, ya2nx2g32xc@networksolutionsprivateregistration.com, yq9r67x579n@networksolutionsprivateregistration.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- bristol.ns.cloudflare.com
- coen.ns.cloudflare.com
MX records
- mxa-004f4901.gslb.pphosted.com
- mxb-004f4901.gslb.pphosted.com
SPF policy
- include: %{ir}.%{v}.%{d}.spf.has.pphosted.com
Threat-feed evidence
History
Related pages
Pivot from otpco.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: "otpco.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.