Hostname
fast.quickcontentnetwork.com
Last fetched
fast.quickcontentnetwork.com resolves to 88.80.17.222, announced in 88.80.16.0/20 by PRQ-AS - Fredrik Holmqvist in SE. fast.quickcontentnetwork.com is listed by 2 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 2 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:20 GMT
- Last seen on a feed
- Tue, 22 Sep 2026 00:51:35 GMT
Nutrition Label
Resolution chain
- 88.80.17.222
88.80.16.0/20 · PRQ-AS - Fredrik Holmqvist · Stockholm, SE
- 94.102.55.18
94.102.55.0/24 · INT-NETWORK - IP Volume inc · Amsterdam, NL
IPv6 resolution
No AAAA record for fast.quickcontentnetwork.com is recorded in WhisperGraph.
Attribution
fredrik holmqvist
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fast.quickcontentnetwork.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
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
- pdns1.registrar-servers.com
- pdns2.registrar-servers.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
- eforward1.registrar-servers.com
- eforward2.registrar-servers.com
- eforward3.registrar-servers.com
- eforward4.registrar-servers.com
- eforward5.registrar-servers.com
SPF policy
- include: spf.efwd.registrar-servers.com
Threat-feed evidence
History
Related pages
Pivot from fast.quickcontentnetwork.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: "fast.quickcontentnetwork.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.