Hostname
telemarktalk.com
Last fetched
telemarktalk.com resolves to 104.21.66.250, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. telemarktalk.com is listed by 2 threat feeds; reconciled level HIGH.
Threat posture
50threat score (procedure-native scale)
HIGHListed by 2 threat feeds. At least one source recommends blocking.
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:51:22 GMT
- Last seen on a feed
- Wed, 09 Sep 2026 00:26:23 GMT
Nutrition Label
Resolution chain
- 104.21.66.250
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.166.141
172.67.160.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.3
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.96.4
188.114.96.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.3
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 188.114.97.4
188.114.97.0/24 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 68.168.113.90
IPv6 resolution
Attribution
Cloudflare
cdn · MAIL_RECEIVER, ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:303
- Registrant organisation
- domain admin
- Contact emails
- pafdisques@yahoo.ca, contact@privacyprotect.org
Subdomains
Showing 12 of 23. View all 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
- armfazh.ns.cloudflare.com
- virginia.ns.cloudflare.com
- ns1am.service-dns.net
- ns2am.service-dns.net
- ns3am.service-dns.net
MX records
- telemarktalk.com
- _dc-mx.2c8b51699c6c.telemarktalk.com
SPF policy
- include: spf.likuid.com
- a: telemarktalk.com
- mx: telemarktalk.com
- ip: 209.44.124.250
- ip: 209.44.124.45
- ip: 67.212.79.130
- ip: 68.168.113.90
Threat-feed evidence
History
Related pages
Pivot from telemarktalk.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: "telemarktalk.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.