Skip to content

Hostname

gold4day.com

Last fetched

gold4day.com resolves to 141.94.37.151, announced in 141.94.0.0/16 by OVH - OVH SAS in FR. gold4day.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 · gold4day.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/gold4day.com

Resolution chain

IPv6 resolution

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

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
domains by proxy,
Contact emails
c6f30b2501e54080a42c116d54dac0fb.protect@withheldforprivacy.com, f69853c6a4ba490692e160b12874e288.protect@withheldforprivacy.com

Subdomains

Subdomain
edu1.gold4day.com
edu2.gold4day.com
edu3.gold4day.com
edu7.gold4day.com
education.gold4day.com
eduno.gold4day.com
mail.gold4day.com
www.gold4day.com

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

  • arch.ns.cloudflare.com
  • lisa.ns.cloudflare.com
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

MX records

  • mx1-hosting.jellyfish.systems
  • mx2-hosting.jellyfish.systems
  • mx3-hosting.jellyfish.systems

SPF policy

  • a: gold4day.com
  • mx: gold4day.com
  • include: spf.web-hosting.com
  • ip: 162.0.235.252

Threat-feed evidence

History

Related pages

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