Skip to content

Hostname

webdesignerhut.com

Last fetched

webdesignerhut.com resolves to 51.81.82.44, announced in 51.81.0.0/17 by OVH - OVH SAS in US. webdesignerhut.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 · webdesignerhut.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/webdesignerhut.com

Resolution chain

IPv6 resolution

No AAAA record for webdesignerhut.com is recorded in WhisperGraph.

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
nagy andor
Contact emails
andornagy2013@gmail.com, dec4a2de34a94c5e8a8c1eca621893c0.protect@whoisguard.com, 700d38a012124426b855348949e4b007.protect@withheldforprivacy.com, daaf17db3c244e67ae3343e7ea534bca.protect@withheldforprivacy.com

Subdomains

Subdomain
www.webdesignerhut.com

Showing 1 of 1 subdomain (1 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

  • emily.ns.cloudflare.com
  • fonzie.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

MX records

  • aspmx1.migadu.com
  • aspmx2.migadu.com

SPF policy

  • include: amazonses.com
  • include: spf.migadu.com

Threat-feed evidence

History

Related pages

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