Skip to content

Hostname

signroots.com

Last fetched

signroots.com resolves to 192.0.78.144, announced in 192.0.78.0/24 by AUTOMATTIC - Automattic, Inc in US. signroots.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 · signroots.comRouting diversity2.4/10Peering density7.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/signroots.com

Resolution chain

IPv6 resolution

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

Attribution

automattic

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
mohammed jaseem
Contact emails
domains@signroots.com

Subdomains

Subdomain
cart.signroots.com
cp.signroots.com
google-workspace.signroots.com
ns1.signroots.com
ns2.signroots.com
ns3.signroots.com
ns4.signroots.com
support.signroots.com
www.signroots.com

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

Mail and authentication

Nameservers

  • ns1.signroots.com
  • ns2.signroots.com
  • ns3.signroots.com
  • ns4.signroots.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • include: sender.zoho-books.in

Threat-feed evidence

History

Related pages

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