Skip to content

Hostname

sidf.gov.sa

Last fetched

sidf.gov.sa resolves to 82.147.197.123, announced in 82.147.192.0/19 by ZAJIL-AS - Etihad Etisalat, a joint stock company in SA. sidf.gov.sa 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 · sidf.gov.saRouting diversity2.4/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/sidf.gov.sa

Resolution chain

IPv6 resolution

No AAAA record for sidf.gov.sa is recorded in WhisperGraph.

Attribution

etihad salam cjsc

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for sidf.gov.sa. 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-awareness.sidf.gov.sa
awareness.sidf.gov.sa
eloan.sidf.gov.sa
eservices.sidf.gov.sa
esign.sidf.gov.sa
fs.sidf.gov.sa
gtmdrmobily.sidf.gov.sa
gtmhqmobily.sidf.gov.sa
gtmhqstc.sidf.gov.sa
hackathon.sidf.gov.sa
login-awareness.sidf.gov.sa
mail.sidf.gov.sa

Showing 12 of 27. 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

  • ns1.bluvalt.sa
  • ns2.bluvalt.sa
  • ns1.itc.net.sa
  • ns2.itc.net.sa

MX records

  • mail.sidf.gov.sa
  • mail2.sidf.gov.sa
  • mail3.sidf.gov.sa

SPF policy

  • include: _spf-dc23.sapsf.com
  • include: _spf-dc82.sapsf.com
  • include: spf.srsa.mail-server.online
  • ip: 212.62.111.133
  • ip: 37.216.239.251
  • ip: 82.147.197.122
  • ip: 91.221.202.3

Threat-feed evidence

History

Related pages

Pivot from sidf.gov.sa 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: "sidf.gov.sa"})-[: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.