Skip to content

Hostname

designcode.io

Last fetched

designcode.io resolves to 18.208.88.157, announced in 18.208.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. designcode.io 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 · designcode.ioRouting diversity2.4/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/designcode.io

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:625
Registrant organisation
meng to

Subdomains

Subdomain
api.designcode.io
app.designcode.io
beta.designcode.io
develop.designcode.io
ds.designcode.io
help.designcode.io
learn.designcode.io
v1.designcode.io
www.designcode.io

Showing 9 of 9 subdomains (9 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

  • dns1.p03.nsone.net
  • dns2.p03.nsone.net
  • dns3.p03.nsone.net
  • dns4.p03.nsone.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

MX records

  • mx.designcode.io.cust.b.hostedemail.com
  • mx1.mail.name.com
  • mx2.mail.name.com
  • mx3.mail.name.com

SPF policy

  • include: _spf.firebasemail.com
  • include: _spf.hostedemail.com
  • a: designcode.io
  • mx: designcode.io
  • include: servers.mcsv.net
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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