Skip to content

Hostname

dev.webarq.net

Last fetched

dev.webarq.net resolves to 139.162.28.43, announced in 139.162.0.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in SG. dev.webarq.net is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed 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:49 GMT
Last seen on a feed
Mon, 14 Sep 2026 19:54:16 GMT

Nutrition Label

WHISPER CANON · dev.webarq.netRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/dev.webarq.net

Resolution chain

IPv6 resolution

No AAAA record for dev.webarq.net is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for dev.webarq.net. 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
acs-be.dev.webarq.net
advan-be.dev.webarq.net
aeon-fe.dev.webarq.net
aice.dev.webarq.net
airnav-be.dev.webarq.net
airportgeeks.dev.webarq.net
ais-be.dev.webarq.net
ais-fe.dev.webarq.net
alfaland-fe.dev.webarq.net
allfresh.dev.webarq.net
andry.dev.webarq.net
angkasa-corporate-fe.dev.webarq.net

Showing 12 of 306. View all subdomains →

Mail and authentication

Nameservers

  • 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
  • ns1.webarq.net
  • ns2.webarq.net
  • ns3.webarq.net
  • ns4.webarq.net

Threat-feed evidence

History

Related pages

Pivot from dev.webarq.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: "dev.webarq.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.