Skip to content

Hostname

sgs-engineering.com

Last fetched

sgs-engineering.com resolves to 104.18.33.147, announced in 104.18.33.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. sgs-engineering.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 · sgs-engineering.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/sgs-engineering.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
andy wyatt
Contact emails
andy@sgs-engineering.com, 330785f63a364b868cf89ca503357669.protect@whoisguard.com, c4f39edc06434e06a1f0f5f9b3519e0e.protect@withheldforprivacy.com

Subdomains

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

  • dahlia.ns.cloudflare.com
  • piotr.ns.cloudflare.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

  • sgsengineering-com0i.mail.protection.outlook.com

SPF policy

  • ip: 104.239.138.114/32
  • ip: 50.56.156.88/32
  • include: spf.protection.outlook.com
  • include: sgs-engineering.com
  • include: mail.zendesk.com
  • include: servers.mcsv.net
  • include: sendgrid.net
  • include: 54.72.121.147

Threat-feed evidence

History

Related pages

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