Skip to content

Hostname

gorodnet.com

Last fetched

gorodnet.com resolves to 109.74.198.240, announced in 109.74.192.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in GB. gorodnet.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 · gorodnet.comRouting diversity1.5/10Peering density4.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/gorodnet.com

Resolution chain

IPv6 resolution

Attribution

akamai

ORIGIN_AS

WHOIS identity

Registrar
iana:895
Registrant organisation
contact privacy inc. customer 124300859
Contact emails
aiwntrmute@msn.com, flmipli7leit@contactprivacy.email, 12f04a5da2a2a7b4720dcd5509b02978395eecb10c85c7e9e437c1cf3c7dcb6f@gorodnet.com.whoisproxy.org

Subdomains

Subdomain
bg.gorodnet.com
by.gorodnet.com
kg.gorodnet.com
kz.gorodnet.com
lt.gorodnet.com
mail.gorodnet.com
md.gorodnet.com
ua.gorodnet.com
uz.gorodnet.com
www.gorodnet.com
zarubezh.gorodnet.com

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

  • ns-cloud-c1.googledomains.com
  • ns-cloud-c2.googledomains.com
  • ns-cloud-c3.googledomains.com
  • ns-cloud-c4.googledomains.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • mx: gorodnet.com
  • ip: 109.74.198.240
  • ip: 2a01:7e00:0:0:f03c:91ff:fe89:e872

Threat-feed evidence

History

Related pages

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