Skip to content

Hostname

macscripter.net

Last fetched

macscripter.net resolves to 45.55.96.103, announced in 45.55.96.0/22 by DIGITALOCEAN-ASN - DigitalOcean, LLC in US. macscripter.net 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 · macscripter.netRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/macscripter.net

Resolution chain

IPv6 resolution

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
domains@geeksuit.com, pw-126de2677342e5101f09a55399f67422@privacyguardian.org, pw-9961567b547e5c82577b9bf20bf8903b@privacyguardian.org, pw-9ab4f466d4f396e412c80d16bcce61d1@privacyguardian.org, pw-9e5598ec5844df46bbc6dac3bf6991e2@privacyguardian.org, pw-aee2958c4b93399b5a54e8e4b1e2d850@privacyguardian.org, pw-c72d50e5696c8aba062379879164d5f5@privacyguardian.org, pw-d67ff9feaa290a479bebdd3e2b495e41@privacyguardian.org

Subdomains

Showing 1 of 1 subdomain (1 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.

Mail and authentication

Nameservers

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

  • mx1.emailsrvr.com
  • mx2.emailsrvr.com

SPF policy

  • include: emailsrvr.com

Threat-feed evidence

History

Related pages

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