Skip to content

Hostname

senator.md

Last fetched

senator.md resolves to 81.169.207.199, announced in 81.169.128.0/17 by STRATO - Strato GmbH in DE. senator.md 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 · senator.mdRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/senator.md

Resolution chain

IPv6 resolution

No AAAA record for senator.md is recorded in WhisperGraph.

Attribution

strato

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for senator.md. 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
afex.senator.md
case.senator.md
compass.senator.md
eon.senator.md
mail.senator.md
ns.senator.md
ns2.senator.md
ro-ecom.senator.md
wildcard.senator.md
wolle.senator.md
www.senator.md

Showing 11 of 11 subdomains (11 per page).

Mail and authentication

Nameservers

  • ns.senator.md
  • ns2.senator.md
  • 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

  • mail.senator.md

SPF policy

  • a: senator.md
  • mx: senator.md
  • ip: 2a01:238:426d:100:0:0:0:0
  • ip: 2a01:238:426d:100:3c27:f889:a7c8:6891
  • ip: 2a01:238:426d:100:3c27:f889:a7c8:6892
  • ip: 2a01:238:426d:100:3c27:f889:a7c8:6893
  • ip: 46.55.84.48
  • ip: 81.169.204.198
  • ip: 81.169.207.199

Threat-feed evidence

History

Related pages

Pivot from senator.md 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: "senator.md"})-[: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.