Dataweaz

fujitsu.com

Summary

Registrar
SafeBrands SAS
Status
clientTransferProhibited
Created on
March 22, 1994
Expires on
March 23, 2027
Name servers
a4-67.akam.net, a5-64.akam.net, a1-171.akam.net, a10-64.akam.net, a3-66.akam.net, a22-65.akam.net
Mail servers
fujitsu-com.mail.protection.outlook.com
DMARC
Reject

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from fujitsu.com but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
[email protected]

Record

v=DMARC1; p=reject; sp=none; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]

Authorized senders (SPF)

Neutral

The record gives no instruction for other servers.

SPF lists the servers allowed to send e-mails for fujitsu.com.

RuleValueResult
ip4207.54.90.47Allowed
ip4207.54.90.48Allowed
ip4207.54.90.49Allowed
ip468.232.139.117Allowed
ip468.232.139.130Allowed
ip468.232.139.139Allowed
ip4139.138.61.252Allowed
ip4139.138.61.253Allowed
ip4139.138.36.223Allowed
ip4139.138.36.225Allowed
ip4207.54.90.137Allowed
ip4139.138.37.100Allowed
includespf.protection.outlook.comAllowed
includemktomail.comAllowed
mxfujitsu.comAllowed
includespf.messagelabs.comAllowed
all—Neutral

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 ip4:207.54.90.47 ip4:207.54.90.48 ip4:207.54.90.49 ip4:68.232.139.117 ip4:68.232.139.130 ip4:68.232.139.139 ip4:139.138.61.252 ip4:139.138.61.253 ip4:139.138.36.223 ip4:139.138.36.225 ip4:207.54.90.137 ip4:139.138.37.100 include:spf.protection.outlook.com include:mktomail.com mx:fujitsu.com include:spf.messagelabs.com ?all

E-mail signing (DKIM)

DKIM keys published by fujitsu.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to fujitsu.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from fujitsu.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @fujitsu.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

fujitsu.com  MX  10 mx1.fujitsu.com.
fujitsu.com  MX  20 mx2.fujitsu.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.fujitsu.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

fujitsu.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.fujitsu.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.fujitsu.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.fujitsu.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.fujitsu.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of fujitsu.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

No IP address: the domain does not point to any web server.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
a4-67.akam.net72.246.46.67
a5-64.akam.net95.100.168.64
a1-171.akam.net193.108.91.171
a10-64.akam.net96.7.50.64
a3-66.akam.net96.7.49.66
a22-65.akam.net23.211.61.65

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @fujitsu.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10fujitsu-com.mail.protection.outlook.com52.101.157.40

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.fujitsu.com.

NameContent
fujitsu.comdocusign=68b5cb7d-e8bc-4604-b648-5b005c2c32c0
fujitsu.comdocusign=b0070ed7-9152-4a8c-9839-4883e625b019
fujitsu.comf820fddc-deaa-427a-b4a6-8facadddb58b
fujitsu.comgoogle-site-verification=oMTK1hyh_pxbv9EYJ_iwYzoU6VtpPXpoox_KPQQYC64
fujitsu.comv=spf1 ip4:207.54.90.47 ip4:207.54.90.48 ip4:207.54.90.49 ip4:68.232.139.117 ip4:68.232.139.130 ip4:68.232.139.139 ip4:139.138.61.252 ip4:139.138.61.253 ip4:139.138.36.223 ip4:139.138.36.225 ip4:207.54.90.137 ip4:139.138.37.100 include:spf.protection.outlook.com include:mktomail.com mx:fujitsu.com include:spf.messagelabs.com ?all
fujitsu.comatlassian-domain-verification=/gL0lT5hdh7khWZYaEKlfLwKwBPsEnOwioK5wxEhf729RE2jZ9U2sUIbn4KKVKuL
fujitsu.comTOmZhHCuvaotjc/7ix7ySDvNyqr7y42YQJ/5mhw4pvWsiM9QWvTLvqTted4y1mRV+C6jU1IzWusJvZSfsDEMUA==
fujitsu.comonetrust-domain-verification=30331f62741d446382b802d983daee00
_dmarc.fujitsu.comv=DMARC1; p=reject; sp=none; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]
selector1._domainkey.fujitsu.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtYMWm5MKZ9H63POAPEP0elMXTAAS0dIqKlMXD2D+v4OONipziI+tXlniURYaTB+yAVzWAi9Qx4W18rVGuO8zBkyBL1IpI+tqbC5fDY+1oD8KSNblJ+LI4oE/m8mbJIJkXBsd5J+CrUw6CJS5eBQOsM/3Ay6tFrWVBmSVQswB7T3/6PHoU8ZxaXBOjFd6nQnnjUYL3B2AnpLwzowwwSZWQvC3SPs938Hvwcqplup1QVahEJsENMSEY5lutJQsTiPqgbs3fqsmnnbixcwdryhSmdw35cYOXgZNJWzfYpjtlMOe8eG7NiLOuBtJ0n6p3ezv039yvP6D5rw+5cUDcZHilQIDAQAB;

Related IP addresses

IPv4 addresses used by fujitsu.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
72.246.46.67Name server a4-67.akam.net72.246.46.0/24
95.100.168.64Name server a5-64.akam.net95.100.168.0/24
193.108.91.171Name server a1-171.akam.net193.108.91.0/24
96.7.50.64Name server a10-64.akam.net96.7.50.0/24
96.7.49.66Name server a3-66.akam.net96.7.49.0/24
23.211.61.65Name server a22-65.akam.net23.211.61.0/24
52.101.157.40Mail server fujitsu-com.mail.protection.outlook.com52.101.157.0/24
207.54.90.47Authorized by SPF207.54.90.0/24
207.54.90.48Authorized by SPF207.54.90.0/24
207.54.90.49Authorized by SPF207.54.90.0/24
68.232.139.117Authorized by SPF68.232.139.0/24
68.232.139.130Authorized by SPF68.232.139.0/24
68.232.139.139Authorized by SPF68.232.139.0/24
139.138.61.252Authorized by SPF139.138.61.0/24
139.138.61.253Authorized by SPF139.138.61.0/24
139.138.36.223Authorized by SPF139.138.36.0/24
139.138.36.225Authorized by SPF139.138.36.0/24
207.54.90.137Authorized by SPF207.54.90.0/24
139.138.37.100Authorized by SPF139.138.37.0/24

WHOIS of the domain fujitsu.com

Domain Name: FUJITSU.COM
   Registry Domain ID: 870_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.safebrands.com
   Registrar URL: http://www.brandshelter.com
   Updated Date: 2026-02-19T03:06:39Z
   Creation Date: 1994-03-22T05:00:00Z
   Registry Expiry Date: 2027-03-23T04:00:00Z
   Registrar: SafeBrands SAS
   Registrar IANA ID: 1290
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +33.488662213
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: A1-171.AKAM.NET
   Name Server: A10-64.AKAM.NET
   Name Server: A22-65.AKAM.NET
   Name Server: A3-66.AKAM.NET
   Name Server: A4-67.AKAM.NET
   Name Server: A5-64.AKAM.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T14:29:58Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.