Skip to content

Hostname

krk7.at

Last fetched

krk7.at resolves to 104.21.48.38, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. krk7.at is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:47 GMT
Last seen on a feed
Mon, 21 Sep 2026 23:09:40 GMT

Nutrition Label

WHISPER CANON · krk7.atRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint9.6/10canon.whisper.security/host/krk7.at

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for krk7.at. 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.

Subdomains

Subdomain
m.krk7.at
sitemap.krk7.at
www.krk7.at
www1.krk7.at

Showing 4 of 4 subdomains (4 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.univie.ac.at
  • ns2.univie.ac.at
  • d.ns.at
  • j.ns.at
  • n.ns.at
  • r.ns.at
  • u.ns.at
  • adam.ns.cloudflare.com
  • aron.ns.cloudflare.com
  • sky.ns.cloudflare.com
  • ina1.registrar.eu
  • ina2.registrar.eu
  • ina3.registrar.eu
  • ns1.dyna-ns.net
  • 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

Threat-feed evidence

History

Related pages

Pivot from krk7.at 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: "krk7.at"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.