Skip to content

Hostname

server.birkan.com

Last fetched

server.birkan.com resolves to 66.175.209.179, announced in 66.175.208.0/21 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. server.birkan.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · server.birkan.comRouting diversity1.5/10Peering density6.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/server.birkan.com

Resolution chain

IPv6 resolution

No AAAA record for server.birkan.com is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

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

Mail and authentication

Nameservers

  • damao.ns.giantpanda.com
  • yangguang.ns.giantpanda.com

MX records

  • mail.mailerhost.net

SPF policy

  • ip: fd43:c0d1:c090::/48

Threat-feed evidence

History

Related pages

Pivot from server.birkan.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: "server.birkan.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 20

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