Skip to content

Hostname

sgarchive.grumpy.land

Last fetched

sgarchive.grumpy.land resolves to 104.193.109.94, announced in 104.193.108.0/22 by PRIVATESYSTEMS - PrivateSystems Networks in US. sgarchive.grumpy.land 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 · sgarchive.grumpy.landRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/sgarchive.grumpy.land

Resolution chain

IPv6 resolution

No AAAA record for sgarchive.grumpy.land is recorded in WhisperGraph.

Attribution

privatesystems

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for sgarchive.grumpy.land. 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
mail.sgarchive.grumpy.land
www.sgarchive.grumpy.land

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns1.grumpy.land
  • ns2.grumpy.land
  • 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

  • sgarchive.grumpy.land

SPF policy

  • a: sgarchive.grumpy.land
  • mx: sgarchive.grumpy.land

Threat-feed evidence

History

Related pages

Pivot from sgarchive.grumpy.land 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: "sgarchive.grumpy.land"})-[: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.