Skip to content

Hostname

skul.id

Last fetched

skul.id resolves to 13.226.244.106, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. skul.id 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 · skul.idRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/skul.id

Resolution chain

IPv6 resolution

No AAAA record for skul.id is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for skul.id. 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
api-l12.skul.id
api-lb.skul.id
api-sw1.skul.id
api.skul.id
api2.skul.id
apidocs.skul.id
b2b2c.skul.id
belajar-cms.skul.id
belajar.skul.id
cbt-api.skul.id
cdn.skul.id
dashboard.skul.id

Showing 12 of 31. View all subdomains →

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-442.awsdns-55.com
  • ns-844.awsdns-41.net
  • ns-1208.awsdns-23.org
  • ns-1941.awsdns-50.co.uk

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
  • mx1.hostinger.com
  • mx2.hostinger.com

SPF policy

  • include: _spf.google.com
  • include: _spf.mail.hostinger.com

Threat-feed evidence

History

Related pages

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