Skip to content

Hostname

siedev.net

Last fetched

siedev.net resolves to 104.70.92.253, announced in 104.70.80.0/20 by AKAMAI-AS - Akamai Technologies, Inc. in DE. siedev.net 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 · siedev.netRouting diversity1.5/10Peering density4.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/siedev.net

Resolution chain

IPv6 resolution

No AAAA record for siedev.net is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
domain administrator
Contact emails
domain.master@brights.jp, info@domain-contact.org

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

  • jeff.ns.cloudflare.com
  • kate.ns.cloudflare.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

SPF policy

  • ip: 40.95.0.0/16
  • ip: 211.125.140.0/22
  • ip: 185.183.28.0/22
  • ip: 160.33.194.224/28
  • include: spf.protection.outlook.com
  • a: relay.tbe.taleo.net
  • include: mailgun.org
  • ip: 143.55.149.237
  • ip: 185.132.183.11
  • ip: 185.183.30.70
  • ip: 23.251.237.194
  • ip: 23.251.237.195
  • ip: 23.251.237.196
  • ip: 23.251.237.197
  • ip: 66.159.232.89
  • ip: 66.159.233.14
  • ip: 66.159.233.15
  • ip: 66.159.233.25
  • ip: 66.159.234.101
  • ip: 66.159.234.90
  • ip: 66.159.234.91

Threat-feed evidence

History

Related pages

Pivot from siedev.net 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: "siedev.net"})-[: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.